⚠️ Shift detected GitHub Actions which run jobs using a version matrix. Shift attempted to update your configuration for Laravel 11. However, you should review these changes to ensure the desired combination of versions are built for your package.

⚗️ Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.

To do so, temporarily add Shift's fork to the repositories property of your composer.json:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/filament-fabricator.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:

{
    "require": {
        "z3d0x/filament-fabricator": "dev-l11-compatibility",
    }
}

Finally, run: composer update

PR Summary

• Enhanced Support for Different Branches
  This update allows our tests to run on two new branches (1.x and 2.x) which provides us more flexibility in development and ensures code is working as intended in different versions.

• Updated PHP and Laravel Versions
  Our test matrix, essentially a structure allowing us to test across varying environments, now includes latest and more secure versions of PHP and Laravel. This ensures our app remains compatible and up-to-date.

• Extended Support for Laravel 11.* and Testbench 9.*
  This adjustment to the test matrix broadens our compatibility to the latest Laravel and Testbench versions, increasing the range of environments in which we can properly assess our product.

• Upgraded illuminate/contracts Versions
  The package used to provide core Laravel functionalities has been updated to its ^11.0 version, keeping in line with our updated Laravel support.

• Adjusted Dependency Versions
  Certain key dependencies (nunomaduro/collision and orchestra/testbench) are now compatible with further versions. This gives us more flexibility in development without worrying about compatibility issues.

I provided laravel 11 compatibility to filament-peek and it was released yesterday.
So retriggering the pipeline should actually fix the issue